\frame
{
  \frametitle{Why FindBugs for static analysis research?}
  Working infrastructure for:
    \B
    \item User interface
    \item Bytecode-level static analysis
    \item XML-based format for saved warnings
      \B
      \item Handling multiple versions of software
      \item Tracking warnings over time
      \E
    \E 
  You can focus on developing new analyses, empirical studies, etc.

  Large user base: find out if your idea works in the ``real world''
}


\frame
{
  \frametitle{Research Ideas...}
    \B
    \item Implement new bug detectors
	\B
	\item API specific (e.g., structs, Swing, Hibernate)
	\item General purpose (e.g., deadlock)
	\E
    \item Annotations for defect detection
    \item Explore how developers interact with static analysis
    \E
}
\frame
{
  \frametitle{More Research Ideas...}
    \B
    \item Do historical analysis
	\B
	\item When do warnings get introduced, removed
	\item Correlation between unit tests and field failures and defect warnings
	\item Correlation code coverage, churn, metrics and warnings
	\item Correlation between style and defect warnings
	\E
    \item Improve presentation/UI for static analysis
    \item When does bad code cause the software to behave badly?
    \E
}

